This run includes unresolved review comments on PR #112 in repository https://github.com/leadforge-dev/leadforge

For each unresolved review comment, recommend one of: resolve as irrelevant, accept and implement
the recommended solution, open a separate issue and resolve as out-of-scope for this PR, accept and
implement a different solution, or resolve as already treated by the code.

After I reply with my decision per item, implement the accepted actions, resolve the corresponding
PR comments, and push all of these changes in a single commit.

# Copilot Comments

## COPILOT-1
Location: leadforge/schema/dictionaries.py
URL: https://github.com/leadforge-dev/leadforge/pull/112#discussion_r3393474594
Status: outdated
Root author: copilot-pull-request-reviewer

Comment:
    The module docstring still references `leadforge.schema.features.LEAD_SNAPSHOT_FEATURES`, but that symbol now lives under `leadforge.schemes.lead_scoring.features`. Updating this keeps the documentation accurate after the schema split.

## COPILOT-2
Location: tests/schemes/lead_scoring/test_tasks.py:7
URL: https://github.com/leadforge-dev/leadforge/pull/112#discussion_r3393474639
Status: outdated
Root author: copilot-pull-request-reviewer

Comment:
    This test file is described as testing `leadforge.schema.tasks`, but it imports the shared `SplitSpec` primitive via the lead-scoring scheme module. Import `SplitSpec` from `leadforge.schema.tasks` to keep the primitive’s canonical location and avoid an unnecessary dependency on the lead-scoring scheme.

## COPILOT-3
Location: tests/schemes/lead_scoring/test_features.py:11
URL: https://github.com/leadforge-dev/leadforge/pull/112#discussion_r3393474665
Root author: copilot-pull-request-reviewer

Comment:
    `FeatureSpec` is a shared primitive that lives in `leadforge.schema.features`. Importing it from `leadforge.schemes.lead_scoring.features` makes the test depend on a scheme-specific module and obscures the intended boundary.

## COPILOT-4
Location: tests/schemes/lead_scoring/test_entities.py:12
URL: https://github.com/leadforge-dev/leadforge/pull/112#discussion_r3393474684
Root author: copilot-pull-request-reviewer

Comment:
    `AccountRow` is explicitly a shared entity-row primitive kept in `leadforge.schema.entities`. Importing it from `schemes.lead_scoring.entities` adds an unnecessary dependency on the lead-scoring scheme and makes it easier to accidentally treat shared primitives as scheme-specific.

## COPILOT-5
Location: tests/schemes/lifecycle/test_entities.py:17
URL: https://github.com/leadforge-dev/leadforge/pull/112#discussion_r3393474693
Root author: copilot-pull-request-reviewer

Comment:
    `AccountRow` and `FKConstraint` are shared primitives that remain in `leadforge.schema.*`. Importing them from lead-scoring scheme modules couples the lifecycle tests to the lead-scoring scheme and undermines the intended split between shared primitives and scheme-specific catalogs.

## COPILOT-6
Location: leadforge/narrative/dataset_card.py:15
URL: https://github.com/leadforge-dev/leadforge/pull/112#discussion_r3393474722
Root author: copilot-pull-request-reviewer

Comment:
    `FeatureSpec` is a shared primitive defined in `leadforge.schema.features`. Importing it from `leadforge.schemes.lead_scoring.features` makes this scheme-agnostic narrative renderer depend on a scheme module unnecessarily.